ci: migrate registry-image resources from Docker Hub to GHCR#447
Merged
Conversation
Switch all three registry-image resources from docker.io to
ghcr.io/cloudfoundry using the github_read_write_packages credential
already in CredHub:
docker.io/bosh/agent → ghcr.io/cloudfoundry/bosh-agent
docker.io/bosh/main-postgres-15 → ghcr.io/cloudfoundry/bosh/main-postgres-15
The integration-postgres-15 change fixes "Invalid CPI response - unexpected
end of input" failures that started after the dummy CPI was extracted upstream.
The GHCR image has `bundle config set --global path "${GEM_HOME}"` baked in,
so bundled gems land in GEM_HOME; the CPI wrapper (cpi.erb) exports GEM_HOME
into the subprocess, letting `require 'bundler/setup'` and `require 'cloud'`
find all gems. Verified: bosh-integration-tests build 601 succeeded (1h9m,
0 failures) after this change.
The bosh-agent image migration avoids Docker Hub rate limits for all CI tasks.
Note: ghcr.io/cloudfoundry/bosh-agent does not exist yet. After merging,
manually trigger build-docker-image once to bootstrap the GHCR package; all
downstream jobs will then trigger normally via bosh-agent-registry-image.
Resource types (bosh-deployment-resource, metalink-repository-resource,
semver-resource) remain on Docker Hub — no GHCR equivalents exist for these
Concourse worker plugins.
ai-assisted=yes
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughUpdated the BOSH agent and PostgreSQL integration image resources in the CI pipeline to pull from GitHub Container Registry. Both resources now use the 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Concourse pipeline to pull/push the pipeline’s registry-image resources from GitHub Container Registry (ghcr.io/cloudfoundry/...) instead of Docker Hub, using the github_read_write_packages credentials.
Changes:
- Migrate
bosh-agent-docker-imageandbosh-agent-registry-imagefromdocker.io/bosh/agenttoghcr.io/cloudfoundry/bosh-agent. - Migrate
integration-postgres-15-imagefromdocker.io/bosh/main-postgres-15toghcr.io/cloudfoundry/bosh/main-postgres-15. - Swap Docker Hub credentials for
github_read_write_packageson the affected resources.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
cf-foundation-community-automation
Bot
moved this to Inbox
in Foundational Infrastructure Working Group
github-project-automation
Bot
moved this from Inbox
to Pending Merge | Prioritized
in Foundational Infrastructure Working Group
ystros
approved these changes
Jul 11, 2026
github-project-automation
Bot
moved this from Pending Merge | Prioritized
to Done
in Foundational Infrastructure Working Group
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switch all three
registry-imageresources fromdocker.iotoghcr.io/cloudfoundry, using thegithub_read_write_packagescredential already in CredHub:bosh-agent-docker-imagedocker.io/bosh/agentghcr.io/cloudfoundry/bosh-agentbosh-agent-registry-imagedocker.io/bosh/agentghcr.io/cloudfoundry/bosh-agentintegration-postgres-15-imagedocker.io/bosh/main-postgres-15ghcr.io/cloudfoundry/bosh/main-postgres-15Resource types (
bosh-deployment-resource,metalink-repository-resource,semver-resource) remain on Docker Hub — no GHCR equivalents exist for these Concourse worker plugins.Why
The
integration-postgres-15GHCR image hasbundle config set --global path "${GEM_HOME}"baked in. This ensures bundled gems land inGEM_HOME, which the CPI wrapper script (cpi.erb) exports into the CPI subprocess environment. Without it,require 'bundler/setup'andrequire 'cloud'silently crash the subprocess, producing theInvalid CPI response - unexpected end of inputfailures that plaguedbosh-integration-testssince build 591.Verified:
bosh-integration-testsbuild 601 succeeded (1h9m, 0 failures across all suites) after switching to the GHCR image.Post-merge action required
ghcr.io/cloudfoundry/bosh-agentdoes not exist yet. After merging and reconfiguring the pipeline, manually triggerbuild-docker-imageonce to bootstrap the package on GHCR. All downstream jobs will then trigger normally viabosh-agent-registry-image.Made with Cursor